Secure peer-to-peer object storage system

ABSTRACT

A peer-to-peer (P2P) networking system is disclosed that provides a large, persistent object repository with the ability to easily scale to significant size. Data security is provided using a distributed object data access mechanism to grant access to data objects to authorized users. Data objects stored within the object repository are provided a plurality of security options including plain text data, objects, encrypted data objects, and secure, secret sharing data objects. A data object query processing component permits users to locate requested information within the P2P networking system.

RELATED PATENTS

This application claims the benefit of U.S. Provisional Application to Marceau et al., entitled, “SECURE ACCESS CONTROL IN A PEER-TO-PEER OBJECT STORAGE SYSTEM USING UNTRUSTED COMPONENTS,” Ser. No. 60/564,057, filed Apr. 21, 2004, the content of which is incorporated herein by reference in its entirety.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

This invention was made with Government support under Contract F30602-03-C-0041 awarded by the U.S. Air Force. The Government may have certain rights in this invention.

TECHNICAL FIELD

The invention relates to distributed data storage systems, and more specifically, to providing secure access to data object storage within peer-to-peer networks.

BACKGROUND

Peer-to-peer (P2P) technology presents an alternative to traditional centralized information systems because of their potential to scale to realistic sizes and their inherent fault-tolerance. In P2P systems, computers communicate directly with each other, rather than through servers that can become performance bottlenecks and single points of failure. Self-organizing P2P networks have proven highly adaptable to changes in network connectivity and resilient to node or network failures. While current P2P technology may provide scalable and robust distributed data object storage, current P2P solutions are not widely used due, at least in part, to security concerns. For example, P2P networks are generally used for freely sharing data, such as information or music. However, P2P networks generally do not provide needed security and access control with query functionality that is required for more sophisticated information systems.

SUMMARY

In general, the invention relates to peer-to-peer (P2P) computer networks used to provide secure data storage and data object retrieval between peer nodes within a peer-to-peer network. For example, as described herein, the invention provides secure access control and integrated query functionality to easily identify and retrieve the data objects. As another example, the invention provides mechanisms for secure storage of objects at even insecure peers within the P2P system.

The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1A is a block diagram illustrating a peer-to-peer (P2P) data storage system according to the present invention.

FIG. 1B is a block diagram illustrating a mapping of data object identifiers to peer node identifiers within a data object storage address space in the P2P data storage system of FIG. 1A.

FIGS. 2A and 2B are block diagrams illustrating an exemplary embodiments of peer nodes within the P2P data storage system of FIG. 1A.

FIGS. 3A-3B are flowcharts illustrating example operation of the P2P clients when processing the remote data access requests.

FIG. 4 is a block diagram illustrating an exemplary data object repository maintained by each node of the P2P data storage system.

FIG. 5 is a flowchart illustrating exemplary data object retrieval operations by the P2P node according to the present invention.

FIGS. 6A-6B are flowcharts illustrating techniques for the encryption and decryption of data objects within the P2P data storage system.

FIG. 7 is a block diagram illustrating an example embodiment of a data object stored by the P2P data storage system.

FIG. 8 is a block diagram illustrating an exemplary organization of data object database for use by a peer node of the P2P data storage system according to the present invention.

DETAILED DESCRIPTION

FIG. 1A is a block diagram illustrating an example peer-to-peer (P2P) data storage system 100 according to the present invention. A plurality of peer nodes 102A-102F (collectively, “peer nodes 102”) are connected to a common communications network 101 to create P2P data storage system 100. Local storage areas 103A, 103B and 103N (collectively, “local storage areas 103”) are coupled to respective peer nodes 102A, 102B and 102N (collectively, “peer nodes 102”).

In general, local storage areas 103 store data objects that may be accessed by software processes executing within any of peer nodes 102. The software processes may be controlled and initiated by principals, i.e., users, who use P2P data storage system 100 to perform data processing tasks. In particular, access requests on behalf of the principals are transmitted between peer nodes 102 to store, retrieve and delete data objects stored within local storage areas 103. Each of the peer nodes 102 applies policies to control the application of the access requests, i.e., whether to accept or reject the access requests. As described herein, this process is performed in a secure manner without use of a centralized network node that maintains control access information.

P2P data storage system 100 is constructed as an overlay network that operates within a distributed computing system connected via communications network 101. For example, network 101 may consist of an Internet Protocol (IP)-based network in which peer nodes 102 exchange data packets or cells using any number of communications protocols, including the transmission control protocol (TCP) or other protocols. Peer nodes 102 maintain P2P routing tables that include network addresses, such as IP addresses, for other peer nodes 102 for use in the exchange of data packets between the various peer nodes.

Fundamentally, P2P data storage system 100 operates on two levels. At a base level, P2P data storage system 100 provides secure object storage for distributed data objects. At this level, P2P data storage system 100 provides insert, lookup, and reclaim capability on individual objects. P2P data storage system 100 makes no assumptions about the objects being stored. At a higher level, P2P data storage system 100 provides retrieval mechanism for location and retrieval of information stored within the data objects. For example, objects may consist of metadata and payload, and P2P data storage system 100 supports query mechanisms to locate objects using the stored metadata.

In accordance with the principles described herein, P2P data storage system 100 provides integrity, availability, and confidentiality for data objects stored within local storage areas 103 in spite of malicious or insecure nodes. In other words, in the event a node is compromised, the malicious acts that can be carried out by the node are limited. For example, the node can alter or destroy the data objects that it stores (threat to integrity); refuse to grant access to authorized principals (threat to availability); grant access to unauthorized principals, such as itself (threat to confidentiality); and examine information objects in transit from a source to a destination node. Nevertheless, the integrity, availability, and confidentiality of data objects throughout P2P data storage system 100 are not compromised.

For example, integrity is ensured by use of self-certifying data objects. In other words, data objects are stored in a manner that allows their authenticity to be easily verified by the recipient. As described below, in one embodiment each data object is associated with an identifier that is a secure hash of its contents, signed by its creator. Therefore, the recipient of a data object can always check its integrity.

Availability is ensured by replication of data objects within multiple network peer nodes 102. If peer node 102A, for example, receives a corrupted data object in response to a query, or its request for an object is denied by a malicious node, peer node 102A may request the data object from one or more different nodes. However, the probability that all peers holding replicas of a given object are compromised is (b/N)^(r), where N is the total number of nodes, b is the number of corrupt nodes, and r is the replication factor. For example, replicas of a data object may be stored at the r nodes whose addresses are closest to the ID of the data object. The parameter r is referred to as a replication factor, and determines a degree of fault-tolerance provided by P2P data storage system 100. As one example, P2P data storage system 100 may have b=5, N=500, r=5, for which the probability of all peers holding a given data object being compromised equals 10⁻¹⁰, which is negligible.

In addition, P2P data storage system 100 provides “secure routing” that allows client 102A, for example, to require that a requested data object travel across network 100 by a different route than previously requested. In this manner, malicious nodes are not able to prevent correct delivery of data objects within P2P data storage system 100. Secure routing ensures that a particular message is eventually delivered, despite the fact that one or more peer nodes 102 may be corrupt, or may drop or misroute the message. Secure routing also ensures that a particular message is delivered to any of peer nodes 102 storing a replica of a given data object.

P2P data storage system 100 provides confidentiality of the contents of the data objects with use of encryption. Many well-known encryption mechanisms may be used to provide a desired level of protection for the data objects. As described herein, encryption keys themselves are stored as “secure data objects.” Moreover, each data object may be divided into multiple components and distributed to different peer nodes 102. In particular, each of these components may be stored as a separate data object in separate peer node 102 in P2P data storage system 100. Because of this a malicious node needs to gain access to all of these separate data objects in order to construct the encryption key used to decrypt an encrypted data objects.

In general, P2P data storage system 100 implements these secure access control mechanisms on top of a P2P infrastructure that provides a name space for objects and peers, file storage, and peer-to-peer message routing. For example, in one exemplary embodiment, P2P data storage system 100 utilizes “FreePastry,” which is open-source code P2P network technology that is freely available from Rice University. Other versions are available from Microsoft Corporation. In general, pastry provides efficient message routing among large numbers of nodes within a P2P network.

FIG. 1B is a block diagram illustrating an example data object address space implemented via P2P data storage system. In particular, FIG. 1B illustrates an exemplary data object address space 122, such as an address space provided by Pastry, in which data object identifiers are mapped to peer node identifiers.

In the illustrated example of FIG. 1B, each peer node 102 (FIG. 1) has an associated identifier (ID), which may an integer selected randomly between 0 and 2¹²⁸−1. Consequently, the address space may be viewed as a ring. P2P data storage system 100 locates target nodes in a series of node-to-node hops without using any centralized or global view of the entire network. In general, the number of hops required to send a message between two nodes is roughly log N, where N is the number of nodes.

The address space serves a double purpose in P2P data storage system 100. First, the address space provides a unique ID for each object and peer node 102. Second, the address space provides a mechanism, such as a distributed hash table (DHT), that can be used to locate one or more peer nodes 102 responsible for a given object ID. For example, data object 131 may be stored on peer node 132, peer node 133 and peer node 134 to provide a desired level of replication.

In an exemplary embodiment, a peer node 102 (FIG. 1) is assigned an ID within the data object address space 122. Data objects are stored at the peer nodes having IDs that are “closest” to the object's object ID. When a particular data object is replicated at r different peer nodes, the particular data object is stored in all peer nodes in which assigned node IDs are one of the “r closest” node IDs for all peer nodes present in the data object address space 122. Peer nodes 102 typically are informed of node IDs for a set of neighboring peer nodes having assigned node IDs closest to each peer node. Using the information identifying the set of neighboring peer nodes and their respective node IDs, peer node 102 may determine if its assigned node ID is one of the “r closest” peer nodes in data object address space 122 for any requested data object.

FIG. 2A is a block diagram illustrating an example embodiment of a peer node, such as peer node 102A of P2P data storage system 100. In this example embodiment, peer node 102A contains a plurality of data processing modules to perform data object storage and retrieval functions within P2P data storage system 100. These processing modules are organized into two separate sets of functions: (1) client-side request processing modules 241, and (2) server-side modules 245.

Network interface module 204 provides a P2P infrastructure and general interface between network 101 and peer node 102A. Network interface module 204, for example, translates data access requests and corresponding responses into individual data packets for transmission over network 101, as well as assembles incoming data access requests and corresponding responses received from other peer nodes 102.

Secure routing module 202 provides secure routing of data objects between peer nodes 102. Secure routing module 202 ensures that a message is delivered to an authorized one of peer node 102 that it is addressed to and that the requested data object is uncompromised. Secure routing module 202 also ensures that the one of peer nodes 102 receiving the message can trust that the identity specified within the message is accurate. Because secure routing ensures these properties, principals receiving and using data objects stored within P2P data storage system 100 may confidently know that unaltered data objects are provided from trusted peer nodes 102 in response to data storage and data retrieval requests. In one embodiment, secure routing module 202 utilizes the secure routing techniques described by M. Castro, P. Drushel, A. Ganesh, A. Rowstron, and D. Wallach, “Secure routing for structured peer-to-peer overlay networks,” OSDI '02, Boston, Mass., 2002, hereby incorporated by reference.

Client modules 241 are a set of processing modules invoked by a principal to store and retrieve data objects from P2P data storage system 100. In the illustrated example, client modules 241 include application processes 207 that generally represent client-side application software that utilizes P2P data storage system 100 to store and retrieve data objects.

Application processes 207 may store data objects within P2P data storage system 100 in plain text form. Alternatively, application processes 207 may invoke encryption module 212 to provide a higher level of security and store the data objects within P2P data storage system 100 in encrypted form.

In practice, when initiating a data access request to store a data object within a different peer node 102, encryption module 212 utilizes a randomly generated encryption key to encrypt the data object before the data object is transmitted across network 101. As a result, an unencrypted version, e.g., a plain text version, of the data object exists only within one of peer nodes 102 that initiates the storage or retrieval data access request.

In order to securely support query functionality, i.e., the ability for a peer node 102 to identify and retrieve a data object without prior knowledge of the specific data object, encryption module 212 supports a technique referred to herein as “secret sharing.” As described in further detail below in reference to FIG. 6A, encryption module 212 randomly generates a set of bit sequences for reconstructing the encryption key. Encryption module 212 stores the bit sequences as separate data objects within P2P data storage network 100. When retrieving an encrypted data object, encryption module 212 retrieves the bits sequences, and reconstructs the key and decrypts the data object. In this manner, the bit sequences are referred to herein as the “secret shares” for an associated data object; these secret shares are stored and must be combined to reconstitute the encryption key. Because the secret shares are stored independently on different peer nodes 102, it essentially impossible for a single malicious node acting alone to reconstitute the key.

In general, server-side modules 245 support two operations on objects: (1) object retrieval, and (2) object storage. For both operations, access control module 203 provides access control decisions associated with data object access requests and metadata index queries. When one of peer nodes 102 issues a query to determine locations for data objects or attempts to store or retrieve data objects, access control module 203 determines whether the one of peer nodes 102 transmitting the data access request is authorized to perform the data object access. Specifically, access control module 203 compares certificates provided by the requesting one peer node 102 with certificates 232 to verify the principal's claim that it is authorized to perform the requested operation. Once access control module 203 grants access to local storage area 103A, the data object access request is processed within peer node 102A.

In this manner, policies 231 may be used to establish the access rights for each data object. If the set of provided peer node certificates, together with the policy and the requested data object metadata, enables peer node 102A to complete a proof that supports the request, then peer node 102A grants the data access request. In the case of data object storage, access control module 203 checks that a principal requesting the storage is listed as the publisher in the object's metadata, and that the digest is consistent with the data object's contents.

Storage access module 211 provides a programming interface between peer node 102A and local storage area 103A. For example, storage access module 211 accesses local storage area 103A to store or retrieve data objects in response to requests from client modules 241 on any peer node 102 in P2P data storage system 100 once access control module 203 has granted permission for the requested access.

Query processing module 206 and metadata indexes 261 identify data objects in response to queries made against metadata associated with the data objects, thereby allowing data objects to be identified for retrieval. Query processing module 206 receives data object query requests from network interface module 204 that are sent by any “client,” i.e., client-side modules 241 executing on any peer node 102 in P2P data storage system 100. In other words, client-side modules 241 issue queries to identify data objects within system 100 having metadata satisfying certain metadata constraints. P2P data storage system 100 maintains a metadata index 261 for each type of data objects, and each metadata index may be replicated on two or more peer nodes 102. As a result, the metadata indexes permit query processing module 206 to efficiently identify data objects having metadata entries that satisfy a particular query request.

FIG. 2B is a block diagram illustrating another exemplary embodiment of peer nodes 102. In particular, FIG. 2B illustrates three peer nodes 102A, 102B and 102N. Each peer node 102 may generally be viewed as including client modules 270 (e.g., software applications) that invoke client interface 272. In turn, client interface (CLIENT IFC 272 in FIG. 2B) provides an interface to the functionality described herein. Collectively, client modules 270 and client interface 272 are viewed as a “client” of P2P data storage system 100.

As shown in FIG. 2B with respect to peer node 102B, each peer node exhibits both “client-side” and “server-side” functionality. Moreover, each peer node 102 accepts client requests and forwards them to the appropriate node for service. For example, to respond to an access query, client-side modules of peer node 102B issues a request 277 to server-side modules of peer node 102A, which holds the metadata index for the requested type in order to the get the data object identifiers of the requested data objects. Peer node 102B then issues request 239 to retrieve the data objects from peer node 102N.

In general, a store operation proceeds in similar manner. For example, a first communication is used to store the metadata in one or more metadata indexes, while a second communication is used to store the object at one or more nodes. Although not illustrated in FIG. 2B, encryption and decryption are performed on the “client-side” of peer nodes 102. Sensitive objects are encrypted prior to being stored.

FIG. 3A-3B are flowcharts illustrating in further detail the operations involved in processing remote data access requests of data objects within P2P data storage system 100. FIG. 3A, for example, is a flowchart that further illustrates the data object retrieval operation shown in FIG. 2B.

The data object retrieval operation typically begins with software modules executing on peer node 102B, e.g., client modules 272, issuing a query. The query may, for example, take the form of a SQL database query (320). In response, peer node 102B determines the type of data object requested, and issues request 277 for the corresponding object ID for the desired data object (322). A node storing the metadata index for the requested type, such as peer node 102A, receives the requests and may reject the request if the principal associated with peer node 102B is not authorized to retrieve the type of data object (324, 325).

If the requesting principal is authorized, peer node 102A determines the object ID and returns the object ID to 102B (326). Peer node 102B then issues request 279 to peer node 102N to retrieve the desired object (332). Peer node 102B may not successfully receive the requested the data object for several reasons. As one example, peer node 102B may receive a response, but may determine that the integrity of the returned data object has been compromised. Other reasons include message routing errors, network faults, data integrity issues, or other reasons.

In the event peer node 102B does not successfully receive a response carrying the requested the data object, peer node 102B may attempt to retrieve a replica of the data object from another peer node known to contain a copy of desired data object (332). When peer node 102B is satisfied that the data object was successfully received (334), the data object retrieval operation ends. Peer node 102B now possesses the data object for subsequent use.

FIG. 3B is a flowchart illustrating a data object storage request operation in which a peer node issues a request to store a data object, e.g., by issuing a data object insert operation or a data object publish operation. Again, for exemplary purposes, the flowchart is described in reference to FIG. 2B.

Peer node 102B, for example, begins the storage operation by generating an object ID corresponding to a data object (341). For example, peer node 102B may generate the object ID by applying a hash function to the content of the data object to generate an address within the data repository address space of P2P data storage system 100. This object ID corresponds to a unique identifier for the data object, and is used to locate peer nodes storing data objects having that particular object ID.

Once the object ID corresponding to the data object is known, peer node 102B issues a storage request 277 to one or more nodes (e.g., peer node 102A) that store a metadata index for the type of data object to be stored (342). In response, peer node 102A determines whether the requesting principal is authorized to store data objects of the specified type (344). In not, peer node 102A rejects the request (345). Peer node 102A may also verify the metadata contained within the data object. For example, the metadata may contain author information regarding the creator of the data object. Peer node 102A may verify this author information to determine whether the actual author of the data object is indeed requesting the storage operation.

If the principal is authorized, peer node 102A updates the locally maintained metadata index for the object type for use in subsequent identification and retrieval of the data object (346). Next, peer node 102B determines the identity of one or more peer nodes to store the data object itself (or replicas thereof), and transmits a respective request 279 to each of the peer nodes. In response, the receiving peer nodes, such as peer node 102N, store the replicas of the data object within their local storage (350). As a result, each of these peer nodes obtain a copy of the data object to provide a desired level of data redundancy for the data object. As part of the storage operations for the data object, each of the receiving peer nodes 102 may verify the contents and metadata for the data object to check for data integrity. This verification process may include computation of an object ID from the contents of the data object to determine if its contents have been altered.

FIG. 4 is a block diagram illustrating an exemplary local storage 399 of a peer node in which the local storage stores a plurality of data object types according to the present invention. In the illustrated example, local storage 399 stores two types of data objects: (1) plain text data objects 401, and (2) encrypted data objects 402. Both plain text data objects 401 and encrypted data objects 402 contain a copy of metadata used to describe the contents, author and related information useful in identifying data objects.

Plain text data object 401 corresponds to a data object in which its data is stored in plain text, i.e. non-encrypted, form. Consequently, plain text data objects 401 are typically used to store data considered to be routine or not important should peer node 102A be compromised. If an untrusted process gains access to local storage 399, and thus may access plain text data object 401, the contents of these non-secure data objects may be read.

In contrast, another form of data object that may be stored within local storage 399 is illustrated by encrypted data object 402. Encrypted data object 402 contains data stored in an encrypted form to prevent access and use of data within data item 402 should it be accessed by an unauthorized process. Encryption keys used to encrypt and decrypt encrypted data object 402 are stored in multiple shares in other peer nodes 102 to prevent unauthorized decryption and access to contents of encrypted data object 402 if local storage 399 is compromised. Encrypted data object 402 is typically used to store more sensitive data that needs additional protection from unauthorized access. Encrypted data object 402 is typically used for a subset of all data items within local storage 399 as computational overhead is needed to encrypt and decrypt the contents of encrypted data object 402 each time data item 402 is accessed. In determining if data is stored in plain text data object 401 or encrypted data object 402, the computational overhead associated with the encryption/decryption processing is compared to the need to protect the contents of the data item from unauthorized access.

One form of plain text data object is secret shares 403. As described herein, peer nodes 102 support “secret sharing” of randomly generated bit sequences for use in reconstructing encryption keys used in generating encrypted data objects 402. The bit sequences for an associated data object are stored independently in plain text form on different peer nodes 102 and are protected by access control.

FIG. 5 is a flow chart illustrating data object retrieval operations within distributed data storage network 100 in accordance with the data object types described in FIG. 4. In order to perform a data object retrieval operation for a data object having a known object ID, a peer node, such as peer node 102B, first determines the data object type for the desired data object (501). Depending upon whether a requested data object is a plain text data object 401 or an encrypted data object 402, peer node 102B performs a different set of data object retrieval operations.

For example, if the requested data object corresponds to a plain text data object 401, peer node 102A retrieves the data object as described above in reference to FIG. 3A (502). Once the requested data object is received, peer node 102A may use the requested data object (503).

If the requested data object corresponds to an encrypted data object 402, peer node 102A performs a query and retrieves the encrypted data object 402 in similar manner (521). In addition, peer node 102A performs queries to retrieve the independent secret shares 403 needed to reconstruct the encryption key associated with the retrieved encrypted data object 402 (522). After retrieving the corresponding secret shares 403, which are stored as independent data objects, peer node 102A reconstructs the encryption key and decrypts the data object (523, 524). Using this arrangement, a decrypted version of encrypted data object 402 and a complete version of the encryption key are never transmitted across the network in a plain text form.

FIGS. 6A-6B are flowcharts illustrating in further detail an example process of encrypting and decrypting of data objects using secret shares within distributed data storage system 100. FIG. 6A, for example, illustrates an example client-side process for the encryption of a data object. For purposes of illustration, FIGS. 6A-6B will be discussed in reference to FIG. 2A.

Initially, a peer node 102, such as peer node 102B, creates a sensitive data object O (611). Next, peer node 102 invokes encryption module 212 to randomly generate an encryption key K (612). Next, encryption module 212 encrypts the data object using the key K (613), thereby producing an intermediate encrypted data object, O_(crypt). Peer node 102B next generates M shares S_(j), each of which is a random bit sequence the same size as K (614). Peer node 102B then constructs S_(XOR), by performing the exclusive-or (XOR) of key K with the M random bit sequences (615). S_(XOR) may be viewed as an intermediate bit sequence that can be used to reconstitute the encryption key, provided the shares S_(j) are known.

Peer node constructs a data object O_(master) containing O_(crypt), S_(XOR), and the addresses of each of the secret share data objects 403 (616). As discussed above, the address of each of the secret share data objects 403 is computed by a hashing algorithm on the contents of the respective objects. Once completed, peer node 102B stores O_(master) and the bit sequences S_(j) within P2P data storage system 100 as data objects. The master object and all the shares may also be replicated for fault-tolerance as any other data object stored within local storage 399 would be similarly replicated.

In this manner, the bit sequences S_(j) are the “secret shares” for an associated data object that are stored and must be combined to reconstitute the encryption key. Because the shares S_(j) are stored independently on different peer nodes 102, it is essentially impossible for a single malicious node acting alone to reconstitute the key.

FIG. 6B is a flowchart illustrating the receipt and subsequent decryption of a data object. Initially, peer node 102A obtains a copy of O_(master) from another peer node storing the data object, extracts O_(crypt), S_(XOR), and the addresses of the secret share data objects used to store the encryption key (621). Peer node 102B next requests copies of each of the S_(j) shares (622). Upon receiving the shares, peer node 102A performs an XOR of the secret shares and S_(XOR) to reconstruct the encryption key K (623). Using encryption key K, peer node 102A decrypts O_(crypt) locally, and recovers a plain text version of the retrieved data object O (624).

In accordance with the principles described herein, other secret sharing schemes may be used, such as those described in Blakley, G. R. “Safeguarding Cryptographic Secrets,” in AFIPS 1979 NCC, 1979. Arlington Va. and in Shamir, A., “How to Share a Secret,” Communications of the ACM, 1979, vol. 22: p. 612-613, herein incorporated by reference.

FIG. 7 is a block diagram illustrating an example embodiment of a data object for use within P2P data storage system 100. In the illustrated embodiment, data object 701 has a metadata block 702 and an object data payload 703. The object data payload 703 contains data associated with data object 701 for use when data object 701 is accessed.

Metadata block 702 contains an object ID field 711, an object type field 712, and at least one object metadata attribute field 713. Object ID field 711 contains the object ID for data object 701. This object ID corresponds to the object ID used when storing and accessing the data object from a local storage area 103A.

Object type field 712 contains data used to identify a type of data object. Data objects stored within local storage area 103A may be identified by one of a plurality of data types. Data objects of a common object type possess a common set of object metadata attributes stored within object metadata attribute field 713.

For example, a set of object metadata attributes stored within object metadata attribute field 713 may include identity of an author of data object, date of creation of data object 701, data of last modification of data object 701, and keyword description data used to describe the contents of data object 701. In an exemplary embodiment, metadata is stored, and subsequently searched, as a set of metadata attribute-attribute value pairs. Metadata values stored within object attribute field 713 correspond to the attribute value item of the pair. The metadata attribute of the attribute-value pair is specified when a type of data object metadata identified in object type field 712 is defined. The set of object metadata attributes may be used to search local storage area 103A to locate data objects meeting defined search criteria. In this manner, the object metadata attributes provide a mechanism for peer nodes 102 to determine object IDs corresponding to data objects of interest. Once the object IDs for these data objects are known, the data objects of interest may be retrieved and used using the techniques described above. In one embodiment, the object metadata attributes may be stored within a database for efficient searching using any well-known data query language.

In alternate embodiments, searchable attributes and their corresponding attribute values may be specified as a hierarchical data structure using XML or similar mark-up languages. In these alternate embodiments, the attribute values may be determined and corresponding data objects possessing metadata values satisfying a request query identified using well-known searching techniques corresponding to the storage and specification of the metadata. These alternate metadata specification and storage mechanisms may be used without departing from the present invention.

FIG. 8 is a block diagram illustrating an example scheme for metadata indexes for use by peer nodes 102 within P2P data storage system 100. In the illustrated example, each metadata indexes 812 stores object metadata attributes for a different object type. In other words, each metadata index 812 corresponds to different object type, and each metadata index may be replicated on two or more peer nodes 102. Metadata indexes 812 may, for example, be stored within a relational database. Data objects are stored within data object storage 813, e.g., as files on a local storage.

Client modules executing on peer nodes 102 issue metadata queries to identify data objects matching a particular search query. As a result, metadata indexes 812A-812N permit efficient identification of data objects matching a particular search query. Results from the particular search query include a set of object IDs corresponding to the data objects that satisfy the search query. Using this set of object IDs, peer nodes 102 may retrieve any or all of the data objects. Peer nodes 102 updates object type metadata indexes 812A-812N when data objects are created, modified or deleted.

Various embodiments of the invention have been described. These and other embodiments are within the scope of the following claims. 

1. A distributed data storage system comprising: a plurality of peer nodes coupled by a communications network to form a peer-to-peer computing network; and a plurality of storage areas that stores data objects, each of the plurality of storage areas being coupled to a corresponding one of the plurality of peer nodes, wherein each of the plurality of peer nodes includes: one or more metadata indexes that store metadata associated with the data objects, a query processing module that processes queries from the other peer nodes and identifies one or more of the data objects based on metadata constraints specified within the queries, and an access control module that controls access to the data objects.
 2. The distributed data storage system according to claim 1, wherein peer nodes store each of the data objects in one of a plurality of formats in accordance with a security level associated with each of the data objects.
 3. The distributed data storage system according to claim 1, wherein the peer nodes store at least one of the data objects within the storage areas as a high security data object by: dividing the high security data object into a plurality of data object components; and storing each of the plurality of data object components as separate data objects within storage areas coupled to different peer nodes of the plurality of peer nodes.
 4. The distributed data storage system according to claim 1, wherein data objects are stored within the plurality of storage areas as plain text data objects.
 5. The distributed data storage system according to claim 1, wherein data objects are stored within the plurality of storage areas as encrypted data objects.
 6. The distributed data storage system according to claim 5, wherein an encryption key for generating a particular encrypted data object is stored as a set of data objects within the repositories.
 7. The distributed data storage system according to claim 1, wherein each of the data objects is stored using a respective unique object identifier (ID).
 8. The distributed data storage system according to claim 7, wherein the unique object ID corresponds to a hash of contents of the data object.
 9. The distributed data storage system according to claim 7, wherein each of the data objects is stored within one or more of the peer nodes having a peer-to-peer address that is closest to the unique object ID for the data object.
 10. The distributed data storage system according to claim 1, wherein the communication network comprises an IP-based network, and the peer-to-peer computing network is an overlay network on the IP-based network.
 11. A system comprising: a communications network; a plurality of peer nodes coupled by the communications network to form a peer-to-peer network; and a plurality of storage areas, each of the plurality of storage areas being coupled to a corresponding one of the plurality of peer nodes; wherein each of the peer nodes includes an encryption module, and wherein a first one of the peer nodes generates a data object and invokes the encryption module to an encrypted data object prior to transmitting the encrypted data object to a second one of the peer nodes for storage in one of the storage areas.
 12. The system according to claim 11, wherein the encryption module of the first client decrypts the encrypted data object for use within the first peer node after retrieval from the second peer node.
 13. The system according to claim 11, wherein the encryption module of the first peer node generates the encrypted data object using an encryption key, and wherein first client module stores bit sequences for reconstructing the encryption key as data objects within the peer-to-peer network.
 14. The system according to claim 13, wherein the first peer node stores master encrypted data objects within the peer-to-peer communication network, wherein each of the master encrypted data objects includes an intermediate encrypted data objects and a corresponding intermediate bit sequence produced from the encryption key for that intermediate encrypted data object and the corresponding bit sequences.
 15. The system according to claim 11, wherein data objects are stored using a unique object identifier (ID).
 16. The system according to claim 15, wherein the unique object ID corresponds to a hash of contents of the data object.
 17. The system according to claim 15, wherein a data object is stored within one or more peer nodes having a P2P address closest to the unique object ID for the data object.
 18. A system comprising: a plurality of peer nodes forming a peer-to-peer network, wherein each peer node includes a storage area for storing encrypted data objects, and wherein for each encrypted data object the peer nodes store a plurality of bit sequences as data objects within the peer-to-peer network, and retrieve the bit sequences for reconstructing encryption keys associated with the encrypted data objects.
 19. The system according to claim 18, wherein the peer nodes: encrypt original plain text data objects with encryption keys to produce intermediate encrypted data objects; process the encrypted key with the bit sequences to produce an intermediate bit sequence; store master encrypted data objects within the peer-to-peer network, wherein each of the master encrypted data objects includes one of the intermediate encrypted data objects and the corresponding intermediate bit sequence produced from the encryption key of that intermediate encrypted data object; and store the bit sequences as separate data objects within the peer-to-peer communication network.
 20. The system according to claim 18, wherein at least one of the encrypted data objects is encrypted by a first one of the peer nodes prior to transmission to a second one of the peer nodes for storage in the storage area coupled to the second peer node.
 21. The system according to claim 18, wherein the peer nodes randomly generate the bit sequences.
 22. A method comprising: receiving a query from a first peer node of a peer-to-peer (P2P) network requesting identity of a data object associated with a metadata constraint; determining with a second peer node of the P2P network an object identifier corresponding to the data object associated with the metadata constraint; and retrieving with a third peer node the data object corresponding the determined object identifier.
 23. The method according to claim 22, wherein determining with a second peer node comprises: processing the query within a query processing module to compare the metadata constraint against a metadata index; and selecting the object identifier from the metadata index based on the metadata constraint.
 24. The method according to claim 23, wherein the metadata entries correspond to a metadata attribute-value pair.
 25. The method according to claim 24, wherein the metadata entries correspond to hierarchical metadata specified in a mark-up language.
 26. The method according to claim 25, wherein the mark-up language is XML.
 27. The method according to claim 22, wherein the data objects includes a data object payload, and wherein the data object identifier includes: an object ID field; an object type field; and a plurality of metadata attribute fields.
 28. The method according to claim 27, wherein the data object payload comprises plain text data.
 29. The method according to claim 27, wherein the data object payload comprises encrypted data.
 30. The method according to claim 27, wherein the data object payload comprises secret share component data.
 31. The method according to claim 22, wherein the first peer node, the second peer node and the third peer node are the same peer nodes.
 32. The method according to claim 22, wherein the first peer node, the second peer node and the third peer node are three different peer nodes. 